fix: expand Gerrit channel URLs in health score v2 maintainer and development pipes (IN-1229) - #4472

services/libs/tinybird/pipes/health_score_v2_maintainer.pipe:75

• This second channel-producing branch also reads both ReplacingMergeTree sources without FINAL, allowing stale versions to generate duplicate mappings and weight matched fact rows multiple times. Match the canonical repos_to_channels.pipe:41-42 reads.

    FROM repositories r
    INNER JOIN integrations i ON r.sourceIntegrationId = i.id

services/libs/tinybird/pipes/health_score_v2_development.pipe:43

• Both tables in this Gerrit branch are ReplacingMergeTree sources. Without FINAL, stale repository or integration versions create duplicate Gerrit mappings, and the downstream joins count matching facts more than once. This should follow repos_to_channels.pipe:41-42.

    FROM repositories r
    INNER JOIN integrations i ON r.sourceIntegrationId = i.id

services/libs/tinybird/pipes/health_score_v2_development.pipe:17

• This is a change-log note describing what this PR just changed, which the project guideline explicitly disallows because it will become stale as the implementation evolves. Remove this historical note; the node itself should remain the source of truth.

    - Gerrit channel fix (IN-1229): activity rows for Gerrit repos ingested via opendev.org (and
    other Gerrit hosts) are stored under the /q/project: channel variant, not the plain repo URL.
    Added a `channels` node that expands each repo URL to all its possible channel forms — matching
    the logic in repos_to_channels.pipe — so joins against activityRelations, pull_requests_analyzed,
    and issues_analyzed correctly match Gerrit activity.

services/libs/tinybird/pipes/health_score_v2_maintainer.pipe:42

• This is a change-log note describing what this PR just changed, which the project guideline explicitly disallows because it will become stale as the implementation evolves. Remove this historical note; the node itself should remain the source of truth.

    - Gerrit channel fix (IN-1229): activity rows for Gerrit repos ingested via opendev.org (and
    other Gerrit hosts) are stored under the /q/project: channel variant, not the plain repo URL.
    Added a `channels` node that expands each repo URL to all its possible channel forms — matching
    the logic in repos_to_channels.pipe — so joins against activityRelations, pull_requests_analyzed,
    and issues_analyzed correctly match Gerrit activity. isGerrit now derived from

services/libs/tinybird/pipes/health_score_v2_raw_inputs_snapshot.pipe:27

• This changelog-style note documents the change just made, which the repository guideline explicitly disallows in code comments. Remove it; IN-1229 and the PR description already preserve this history.

    - Gerrit channel fix (IN-1229): mirrors the same fix applied to health_score_v2_maintainer.pipe
    and health_score_v2_development.pipe — all activityRelations, pull_requests_analyzed, and
    issues_analyzed joins now route through a `channels` node that expands each Gerrit repo URL to
    its /q/project: variant so Gerrit activity is correctly matched.

services/libs/tinybird/pipes/health_score_v2_maintainer.pipe:42

• This changelog-style note documents the change just made, which the repository guideline explicitly disallows in code comments. Remove it; IN-1229 and the PR description already preserve this history.

    - Gerrit channel fix (IN-1229): activity rows for Gerrit repos ingested via opendev.org (and
    other Gerrit hosts) are stored under the /q/project: channel variant, not the plain repo URL.
    Added a `channels` node that expands each repo URL to all its possible channel forms — matching
    the logic in repos_to_channels.pipe — so joins against activityRelations, pull_requests_analyzed,
    and issues_analyzed correctly match Gerrit activity. isGerrit now derived from

services/libs/tinybird/pipes/health_score_v2_development.pipe:17

• This changelog-style note documents the change just made, which the repository guideline explicitly disallows in code comments. Remove it; IN-1229 and the PR description already preserve this history.

    - Gerrit channel fix (IN-1229): activity rows for Gerrit repos ingested via opendev.org (and
    other Gerrit hosts) are stored under the /q/project: channel variant, not the plain repo URL.
    Added a `channels` node that expands each repo URL to all its possible channel forms — matching
    the logic in repos_to_channels.pipe — so joins against activityRelations, pull_requests_analyzed,
    and issues_analyzed correctly match Gerrit activity.

services/libs/tinybird/pipes/health_score_v2_maintainer.pipe:51

• This duplicates the Gerrit URL expansion already owned by repos_to_channels.pipe:35-88, and the same copy is added to the other two health-score pipes. Any future Gerrit URL rule must now be kept in four implementations or these scores will silently diverge. Please expose a shared repository-to-channel mapping node/pipe (including repoUrl and the metadata needed here) and consume it from all three calculations.

    SELECT

services/libs/tinybird/pipes/repos_channels_copy.pipe:48

• This refresh runs at 01:00, but health_score_v2_raw_inputs_snapshot.pipe runs at 00:30 on the first of each month (line 310). The snapshot therefore reads the previous day's mapping and can omit activity for repositories added or reclassified as Gerrit during that interval. Run this copy before 00:30 so the snapshot uses the current mapping.

COPY_SCHEDULE 0 1 * * *

services/libs/tinybird/pipes/repos_channels_copy.pipe:48

• The daily refresh makes this lookup stale for repository changes between 00:00 and the 02:00/02:10 score runs. A repo created after midnight is still present in the development/final live repository base, but absent from this mapping, so its activity joins miss and its maintainer row is omitted until the following day; platform, exclusion, and deletion updates have the same lag. Refresh this small lookup immediately before consumers (or inline the expansion) rather than claiming the midnight snapshot is always current.

COPY_SCHEDULE 0 0 * * *

services/libs/tinybird/pipes/health_score_v2_raw_inputs_snapshot.pipe:225

• These expanded lifecycle-related inputs now diverge from the label actually computed in health_score_v2_lifecycle.pipe:115-175, which still groups activity relations, issues, and PRs by the raw channel. For Gerrit repositories this snapshot records commits and unanswered activity under the plain repo URL while the production lifecycle pipe sees zero, so validation can reconstruct a different lifecycle state. Route the lifecycle pipe through the same mapping as part of this change.

            FROM activityRelations_deduplicated_cleaned_bucket_union ar
            INNER JOIN repos_channels_ds ch ON ar.channel = ch.channel
            WHERE ar.type = 'authored-commit'

services/libs/tinybird/pipes/health_score_v2_development.pipe:157

• Because repositories is a versioned ReplacingMergeTree, this non-FINAL filter can see an older archived = false/excluded = false version alongside the current ineligible version. That leaves archived or excluded repositories in the development output until a merge happens. Read repositories FINAL for deterministic eligibility.

                                    FROM repositories
                                    WHERE deletedAt IS NULL AND archived = false AND excluded = false

services/libs/tinybird/pipes/health_score_v2.pipe:68

• repositories is a ReplacingMergeTree versioned by updatedAt, so filtering mutable archived/excluded values without FINAL can retain the URL through an older unmerged false row after the current row has been archived or excluded. The aggregate can therefore continue publishing a score for an ineligible repository; read the finalized repository state as the maintainer and signal-detail pipes do.

                    FROM repositories
                    WHERE deletedAt IS NULL AND archived = false AND excluded = false

services/libs/tinybird/pipes/health_score_v2_security.pipe:124

• This eligibility filter reads mutable columns from the versioned repositories datasource without FINAL. Until background merges remove the previous version, an archived or excluded repository still has an older eligible row and continues receiving a security score. Use the finalized repository state here.

                            FROM repositories
                            WHERE deletedAt IS NULL AND archived = false AND excluded = false

services/libs/tinybird/pipes/health_score_v2_lifecycle.pipe:112

• This reads mutable archived and excluded fields from a ReplacingMergeTree without FINAL. If either value changes, old and current versions can coexist; an exclusion can leave the old eligible row, while an archive transition can produce both (url, false) and (url, true) and therefore duplicate/conflicting lifecycle rows. Read the finalized state before DISTINCT.

                    SELECT DISTINCT url, archived
                    FROM repositories
                    WHERE deletedAt IS NULL AND excluded = false

services/libs/tinybird/pipes/health_score_v2_impact.pipe:14

• Filtering excluded on the non-finalized ReplacingMergeTree can match a stale excluded = false version after the repository has been excluded, so the impact pipe still emits the repository contrary to the new eligibility rule. Use FINAL before applying the mutable-state filter.

    FROM (SELECT DISTINCT url FROM repositories WHERE deletedAt IS NULL AND excluded = false) AS base

services/libs/tinybird/pipes/health_score_v2.pipe:68

• This base still includes archived repositories, so the final copy emits archived rows (with category scores missing) even though this PR states archived repos are excluded from the aggregator. Add the archived predicate here to align the materialized output with the component eligibility rules.

                    WHERE deletedAt IS NULL AND excluded = false

services/libs/tinybird/pipes/health_score_v2_maintainer.pipe:187

• Newly recognized custom-domain Gerrit repos with no matching PR row now enter the Gerrit branch, where the existing responsivenessAvailable expression is false when r.repoUrl is empty. Their explicit 0-point responsiveness score is therefore removed from coveredWeight and reweighted away, contradicting the updated description that no changeset data scores 0/15. Make responsiveness available for included Gerrit repos even when the PR aggregate is absent, so this broader classification does not turn a zero into a data gap.

                                (i.platform = 'gerrit') AS isGerrit,

services/libs/tinybird/pipes/health_score_v2_signal_detail.pipe:76

• Archived repositories are still materialized in the signal-detail datasource, contrary to the PR's eligibility rule. Because all three component pipes now omit archived repos, these rows contain only null/default signal values rather than useful detail; filter them from this base as well.

            WHERE deletedAt IS NULL AND excluded = false

services/libs/tinybird/pipes/health_score_v2.pipe:68

• The PR states that archived repositories are excluded from the final aggregator, but this base only filters excluded. As a result, the replace job still emits archived repo rows (with lifecycle/impact data and unavailable category scores). Add the archived predicate so the materialized output matches the declared eligibility policy.

                    WHERE deletedAt IS NULL AND excluded = false

services/libs/tinybird/pipes/health_score_v2_signal_detail.pipe:76

• Archived repositories are also supposed to be removed from the signal-detail datasource, but this base still includes them. Because all three upstream category pipes now exclude archived repos, this produces archived rows whose signal columns are entirely NULL instead of removing those repos.

            WHERE deletedAt IS NULL AND excluded = false

services/libs/tinybird/pipes/health_score_v2.pipe:68

• The PR states that archived repositories are removed from the aggregator, but this base only filters excluded. Because lifecycle and impact intentionally retain archived repositories, the joins still emit an aggregate row for each archived repo (with null category scores). Add the archived predicate here to enforce the documented eligibility rule.

                    WHERE deletedAt IS NULL AND excluded = false

services/libs/tinybird/pipes/health_score_v2_signal_detail.pipe:76

• Archived repositories are still included in the signal-detail base, contrary to the PR's stated rule that both the aggregator and signal-detail outputs exclude them. The three category datasets omit these repos, so this currently materializes misleading all-null detail rows.

            WHERE deletedAt IS NULL AND excluded = false

services/libs/tinybird/pipes/health_score_v2_maintainer.pipe:191

• This new eligibility filter removes excluded repositories entirely, but the file description still says excluded repositories remain present with responsiveness marked blocked (lines 12–14). That methodology documentation is now incorrect and should be removed or updated to describe output-level exclusion.

                            WHERE r.deletedAt IS NULL AND r.archived = false AND r.excluded = false

services/libs/tinybird/pipes/health_score_v2.pipe:68

• Archived repositories are still included in the final aggregator base. Since only the three category pipes filter them, this emits archived rows with null category scores (and potentially lifecycle/impact values), contrary to the PR's stated eligibility rule that the aggregator excludes archived repos. Add the archived predicate here.

                    WHERE deletedAt IS NULL AND excluded = false

services/libs/tinybird/pipes/health_score_v2_signal_detail.pipe:76

• The signal-detail base still admits archived repositories, so it materializes null-only detail rows for repos that the three category datasources now exclude. This contradicts the PR's stated requirement to filter archived repos from signal detail; add the same archived predicate used by the category pipes.

            WHERE deletedAt IS NULL AND excluded = false

services/libs/tinybird/pipes/health_score_v2.pipe:68

• Archived repositories are still emitted by the aggregator because this base only filters excluded. The three category datasources now omit archived repos, so these rows remain in the final output with missing category data (and may still carry lifecycle/impact values), contrary to the PR's eligibility rule that archived repos be removed from the aggregator. Add the archived predicate here as well.

                    WHERE deletedAt IS NULL AND excluded = false

services/libs/tinybird/pipes/health_score_v2_signal_detail.pipe:76

• The signal-detail base still includes archived repositories, even though all three joined category datasources now exclude them. This leaves archived rows containing only null signal fields and contradicts the PR's stated eligibility rule for signal-detail output. Filter archived here too.

            WHERE deletedAt IS NULL AND excluded = false